home *** CD-ROM | disk | FTP | other *** search
- Path: usenet.ucs.indiana.edu!ezinfo!dfetter
- From: dfetter@ezinfo.ucs.indiana.edu (Daniel Fredrick Etter)
- Newsgroups: comp.sys.amiga.hardware
- Subject: PAR and Mercury 040
- Date: 14 Jan 1996 06:01:36 GMT
- Organization: Indiana University, Bloomington
- Message-ID: <4da680$47r@usenet.ucs.indiana.edu>
- NNTP-Posting-Host: ezinfo.ucs.indiana.edu
- NNTP-Posting-User: dfetter
- X-Newsreader: TIN [version 1.2 PL2]
-
-
- Here I am again, asking for more help. I wish someone would ask a
- question I could answer so I wouldn't feel like such a leach, but here
- it goes anyway:
- I have an A3000 w/18 megs on the motherboard, a Merc 040 w/32megs, a
- Toaster, and a VLab. This is a 2.04 ROM system. Before installing the
- PAR, the Merc was working jsut fine. I installed the PAR and it worked
- the first time I tried it. Amazing! Then things went bad. I shut down
- my 3000 and, later, when I turned it back on and ran the PAR software,
- it would load and then bomb. I got the error code #8000 0004. After
- futzing around, I've discovered that I can make the PAR work if I reboot
- in 030 mode. I've also discovered that after awhile the 040 stops
- working. If I leave the 3000 off for awhile, it works again. So what I
- began to suspect was that the heat from the PAR drive (which can get a
- bit toasty) might be fouling the 040. But what is it about the 040 that
- causes the PAR not to work? And why did it work in 040 mode the first
- time I tried it? Any thoughts?
-
- Thanks,
-
- Dan
-
-